Skip to content

Fix #45, #63: Completion text replacement bugs #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 11, 2015

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented Dec 11, 2015

This change resolves a general class of issues around code completions
coming from the language service. The JSON protocol allows the language
server to specify the range of code that will get replaced by a completion
item. Previously this range was being computed incorrectly. We now use
the replacement range given by the PowerShell API.

This also resolves PowerShell/vscode-powershell issues 45 and 12

This change resolves a general class of issues around code completions
coming from the language service.  The JSON protocol allows the language
server to specify the range of code that will get replaced by a completion
item.  Previously this range was being computed incorrectly.  We now use
the replacement range given by the PowerShell API.

This also resolves PowerShell/vscode-powershell issues 45 and 12
daviwil added a commit that referenced this pull request Dec 11, 2015
@daviwil daviwil merged commit ae3ad45 into master Dec 11, 2015
@daviwil daviwil deleted the daviwil/better-completions branch December 11, 2015 18:21
TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this pull request Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants